Release 10.1A: OpenEdge Development:
Progress Dynamics Administration

Deployment stages

The DCU provides a simple mechanism for applying various upgrade programs to a database in a scripted, effective way. Upgrade programs can provide virtually any needed function. Upgrade programs can be invoked at several stages during the process.

Phase 1 of the DCU process uses a specialized subset of the entire Progress Dynamics framework. In general, you should only run programs during Phase 1 that do schema updates and associated tasks on your databases. During this first phase, the DCU writes details of the entire upgrade process to the Repository’s update table.

Whenever the framework starts a new session with a direct database connection for a user who has permission to modify system data, it checks whether there are any outstanding updates. If there are, the second phase of the DCU is invoked when the session starts, and the remaining upgrades are applied. Phase 2 upgrade programs have all the standard Progress Dynamics managers available. However, the environment caches might not have been built yet. ADOs should usually be loaded before the caches are built.

Note: Phase 2 processing does not occur unless both conditions are met. The user must have permission to modify system data, and the new session must have a direct database connection. This means that you cannot initiate Phase 2 processing through an AppServer or WebSpeed connection, for example.

The state of the various caches might affect when you need to run certain upgrade programs. You might also encounter stale data in caches. If an earlier upgrade program changed the data in the Repository, any cache that uses that data is stale. You might want to force the refresh of any needed cached data as the first step in an upgrade program.